Environments
Boomi Event Streams leverages your existing Boomi Integration environments to enhance support for various stages of the development life cycle. Environments created on the Runtime Management page are automatically reflected in Event Streams, making setup and configuration seamless.
Settings
Each Event Streams environment has a Settings tab, alongside Topics and Routes, where you configure the environment's region and manage its tokens.
Regions
Use the Select Region dropdown in the Regions section to choose which Event Streams region this environment uses, then select Save. Event Streams is hosted in four regions: ANZ Event Streams Cloud, DEU Event Streams Cloud, GBR Event Streams Cloud, and USA East Event Streams Cloud.
Changing an environment's region does not delete existing data. Topics, subscriptions, and message backlogs remain in the original region but are not accessible from this environment while it points to a different region. To access them again, switch the environment back to its original region. To move data to the new region, build an integration process to transfer it — region changes do not migrate data automatically.
Tokens
Tokens are used to authorize access to your environments and topics. You can create new tokens for your environments and manage existing tokens in the Tokens table in the Settings tab.
When creating new tokens, you can name your token, assign authorization levels, add descriptions, and set an expiration date for each one, for a maximum of 365 days. The name, description, expiration date, and authorization level of new and existing tokens can be edited and/or deleted.
Once a token is deleted, it cannot be recovered. The delete option is available to Administrators only.
Legacy tokens cannot be edited but can be deleted.
You can also copy new and existing tokens from the Actions column in the tokens table, where you can view their expiration date and other details.
When utilizing the Boomi Event Streams Connector in Integration, Setting environment extensions can be used to override the Environment token in the connector. This enables the connector to dynamically set the appropriate Environment token during deployment, rather than at the individual process or runtime level.
